[MySQL] Extended Support Timeline update#353
[MySQL] Extended Support Timeline update#353andtapia wants to merge 1 commit intoMicrosoftDocs:mainfrom
Conversation
Updated timelines
|
@andtapia : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 9f2b84e: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
There was a problem hiding this comment.
Pull request overview
Updates the Azure Database for MySQL major version retirement/support timeline table to reflect new Standard/Extended Support dates.
Changes:
- Revised Standard Support end dates and Extended Support start/end dates for MySQL 5.7 and 8.0 in the retirement timeline table.
- Adjusted timeline durations to align with the updated extended support plan.
| | [MySQL 5.7](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/) | [Features](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-31.html) | March 20, 2018 | October 31, 2023 | July 31, 2026 | August 1, 2026 | October 31, 2026 | | ||
| | [MySQL 8.0](https://mysqlserverteam.com/whats-new-in-mysql-8-0-generally-available/) | [Features](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-21.html) | December 11, 2019 | April 30, 2026 | Decembber 31, 2026 | January 1, 2027 | April 30, 2029 | |
There was a problem hiding this comment.
The updated table shows Azure Extended Support starting on Aug 1, 2026 (MySQL 5.7) and Jan 1, 2027 (MySQL 8.0), but the next section says Extended Support is planned to begin in spring 2026. Please update the prose to match the revised timelines (or make it version-specific).
There was a problem hiding this comment.
@copilot open a new pull request to apply changes based on this feedback
| | [MySQL 5.7](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/) | [Features](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-31.html) | March 20, 2018 | October 31, 2023 | March 31, 2026 | April 1, 2026 | March 31, 2029 | | ||
| | [MySQL 8.0](https://mysqlserverteam.com/whats-new-in-mysql-8-0-generally-available/) | [Features](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-21.html) | December 11, 2019 | April 30, 2026 | May 31, 2026 | June 1, 2026 | May 31, 2029 | | ||
| | [MySQL 5.7](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/) | [Features](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-31.html) | March 20, 2018 | October 31, 2023 | July 31, 2026 | August 1, 2026 | October 31, 2026 | | ||
| | [MySQL 8.0](https://mysqlserverteam.com/whats-new-in-mysql-8-0-generally-available/) | [Features](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-21.html) | December 11, 2019 | April 30, 2026 | Decembber 31, 2026 | January 1, 2027 | April 30, 2029 | |
There was a problem hiding this comment.
Spelling typo in the date: "Decembber" should be "December".
|
#sign-off |
|
Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @xboxeer |
|
#approve-pr |
1 similar comment
|
#approve-pr |
|
MS employees can't use public repos. closing PR. |
|
#please-close |
Updated timelines